Skip to content

BMC: reconsider lasso-shaped encodings #1202

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

BMC: reconsider lasso-shaped encodings #1202

wants to merge 2 commits into from

Conversation

kroening
Copy link
Member

@kroening kroening commented Jul 13, 2025

This replaces the lasso-shaped encodings in the word-level BMC property encoding. The lasso and straigth-line encodings are now built as separate obligations. In the lasso encoding, all operators follow the same lasso shape. This avoids spurious traces where the eventually operator follows the lasso but a safety part of the property does not.

@kroening kroening force-pushed the bmc-F-encoding branch 13 times, most recently from 657edef to f64a958 Compare July 20, 2025 22:10
@kroening kroening changed the title BMC: reconsider encoding of F BMC: reconsider lasso-shaped encodings Jul 20, 2025
@kroening kroening marked this pull request as ready for review July 21, 2025 11:56
The recursive expansion of the LTL operators R and W is replaced by a loop.
@kroening kroening force-pushed the bmc-F-encoding branch 2 times, most recently from c22fbef to 4c29345 Compare July 23, 2025 20:54
This replaces the lasso-shaped encodings in the word-level BMC property
encoding.  The lasso and straigth-line encodings are now built as separate
obligations.  In the lasso encoding, all operators follow the same lasso
shape.  This avoids spurious traces where the eventually operator follows
the lasso but a safety part of the property does not.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant